This PR addresses markdown-link-check CI failures in currently open PRs that make modifications to Markdown files (*.md), or add new Markdown files:

• Add comprehensive AGENTS.md agent guide #2295
• Move Mikeal Rogers to emeritus #2294

Responding in part to comments in PR #2297:

The justification for excluding the following domains is found by examining recent failing GitHub workflow logs for https://github.com/nodejs/docker-node/actions/workflows/markdown-link-check.yml:

nodejs.org
www.npmjs.com
news.ycombinator.com

Note that the failing results vary according to the response from the remote domains, so multiple workflow logs need to be checked:

https://github.com/nodejs/docker-node/actions/runs/18569189662 shows:

[✖] http://nodejs.org → Status: 403
[✖] https://www.npmjs.com/ → Status: 403
[✖] https://nodejs.org/en/security/ → Status: 403

https://github.com/nodejs/docker-node/actions/runs/18611871299 shows:

[✖] https://www.npmjs.com/ → Status: 403
[✖] https://news.ycombinator.com/item?id=10782897 → Status: 403

For consistency, http://nodejs.org in the README document is updated to use the https protocol instead.

Other use of http could also be migrated, however I suggest to implement this in a separate PR, since it is not related to resolving 403 errors.

Similarly, the suggestion in #2297 to migrate from the npm package markdown-link-check to the GitHub Action tcort/github-action-markdown-link-check is not necessary to solve 403 errors. The action appears to be hardly used and does not track the npm package versions closely. Any migration should be a separate more detailed discussion.

If one of the maintainers would like to enable the workflows awaiting approval, I would expect them to pass.